Architecture for data processing and user experience to provide decision support

ABSTRACT

A system for processing data to generate an output includes an automated tagging system that receives data from a plurality of alternate data providers, each of the plurality of data providers having different types of data; a company financial data unit that provides published information comprising annual reports, press releases, information from the social media of spokespersons or executives, and published pricing information; a modelling system that receives the standardized data of the automated tagging system and the company financial data, the modelling system including one or more handle generators and forecast builders that are applied to the artificial intelligence-based system that employs the neural networks to generate, as an output, a forecast; and a revenue prediction unit that receives the output as the forecast, comprising one or more revenue predictions, to generate a final output as a revenue prediction.

PRIORITY CLAIM TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 17/313,958, filed on May 6, 2021, which claims priority under 35 USC § 119(e) to U.S. Provisional Application Nos. 63/021,550 and 63/171,967, filed on May 7, 2020 and Apr. 7, 2021, respectively, the contents of which are incorporated herein by reference in their entirety.

BACKGROUND Field

The present disclosure relates to systems and methods for measuring data (e.g., revenue) and determining present and future trends, and providing a recommendation based on the measured data and determined trends.

Related Art

In related art systems, data analysts typically study and analyze trends in economic data manually. For example, these analysts may study data in order to determine when to buy or sell a stock manually, or what the unemployment rate looks like at any given period.

However, the data used to determine these metrics may be unreliable due to the lack of availability of such proprietary information. For example, data which should not necessarily be correlated with a particular economic metric may not have been filtered out when analyzing the data, thereby introducing inaccuracies within the analysis.

Thus, there is a need for reliable data, and reliable methods for analyzing the data to determine present and future trends in this data.

SUMMARY OF THE DISCLOSURE

Aspects of the present application may include a server apparatus. The server apparatus may include means for storing collected data and historical data, means for executing operations to achieve functions operations associated with the features disclosed in the detailed description.

According to an aspect, a system is provided for processing data to generate an output, the system comprising: an automated tagging system that receives data from a plurality of alternate data providers, each of the plurality of data providers having different types of data; wherein the automated tagging system standardizes the different types received from the different data providers by performing filtering, de-duplication, normalization, and classification; wherein the automated tagging system performs updating and feedback by providing an artificial intelligence system that employs neural networks that use back propagation for periodic updates to a training phase; a company financial data unit that provides published information comprising annual reports, press releases, information from the social media of spokespersons or executives, and published pricing information; a modelling system that receives the standardized data of the automated tagging system and the company financial data, the modelling system including one or more handle generators and forecast builders that are applied to the artificial intelligence-based system that employs the neural networks to generate, as an output, a forecast; a revenue prediction unit that receives the output as the forecast, comprising one or more revenue predictions, to generate a final output as a revenue prediction.

According to the above aspect, the different types of data comprise financial transaction information, location information, or consumer behavior information.

Further, the input to the modelling system includes proprietary data associated with the merger and acquisition information of the company, and a fiscal quarters calendar of the company.

Yet further, the final output comprises a recommendation to buy, hold or sell, as a transaction, a score, or an execution instruction associated with the transaction without involving the user.

Additionally, a rule-based or other deterministic approach is combined the neural network.

According to another aspect, a system is provided for processing data to generate an output, the system comprising: a plurality of inputs, each of the inputs being received from a data source, and each of the inputs being of a different type; a big data system configured to receive each of the plurality inputs, the big data system including, a plurality of adapters corresponding to the plurality of inputs, each of the adapters configured to normalize, deduplicate and classify the data received from the plurality of inputs, to generate outputs, and a modeling system that receives the generated outputs, and provides the generated outputs to a plurality of multi-panel generators, multi-forecast builders and forecaster modules, to generate a revenue prediction; and an access point and provides the revenue prediction in the format of a file, an API, a console or a custom format.

Further according to this aspect, data miners and analysts supervise and update the plurality of adapters.

Still further, the outputs of the plurality of adapters is combined with external data comprising financial reports or other publicly available information associated with historical or present characteristics of an entity.

According to yet another aspect, a computer-implemented method of processing data is provided, the method comprising: a first phase associated with data processing, the first phase comprising, receiving input data from a plurality of sources of different types, normalizing the received data by mapping the received input data from organic formats in which the was received, to a standardized data format that provides consistency across the organic formats by accounting for the differences in the input data from the plurality of sources of different types, and deduplication, to generate normalized data; applying tagging rules to the normalized data, the tagging rules comprising rules that are specific to a credit card or debit card, geo-fencing rules for GPS data, and rules associated with browser history or application usage, to generated tagged data; a second phase associated with development of a panel and calibration, the second phase comprising, performing panelization by establishing a sample of users as a panel based on one or more of input data churn rate, user transaction patterns, census data balancing, or another rules that associates a characteristic of user transaction behavior with a transaction grouping the panels by symbol to associate one or more brands of a company with the tagged data, wherein the grouping is performed in real time to incorporate mergers, acquisitions, spinoffs, bankruptcies, rebranding, listing or delisting associated with the company associated with the symbol; and applying one or more corrections to the grouped panels by applying one or more respective patterns associated with a financial institution to calibrate the grouping, wherein the respective patterns comprise weekend postings of information, posting delays typically associated with a financial institution, and pending but not yet posted transactions, removing anomalies associated with anomalous transactions or anomalous users; a third phase associated with creating and applying a prediction model, the third phase comprising, generating a prediction model, wherein training data comprises historical data associated with the company including financial parameters of the company, stock price, and historical measurements, generating a forecast by using the generated prediction model and features associated with a current time period, the forecast comprising a prediction of a future stock price.

Further, the input data comprises timeseries data from multiple vendors, including credit card transactions, debit card transactions or other electronic purchase transactions.

Still further, the tagging comprises, for a series of financial transactions, labeling each of the financial transactions by applying the tagging rules to the series of financial transactions, wherein the tagging rules include an inclusive filter or an exclusive filter, and further comprising applying natural language processing based on neural networks.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary implementation(s) of the present invention will be described in detail based on the following figures, wherein:

FIG. 1 illustrates functions of an architecture according to an example implementation of the present application.

FIG. 2 illustrates a structure of an architecture according to an example implementation of the present application.

FIG. 3 illustrates a process associated with an architecture according to an example implementation of the present application.

FIG. 4 illustrates example alternative data types according to an example implementation of the present application.

FIG. 5 illustrates example alternative dataset processing according to an example implementation of the present application.

FIG. 6 illustrates example automatic tagging according to an example implementation of the present application.

FIG. 7 illustrates user experiences according to an example implementation of the present application for a watchlist.

FIG. 8 illustrates processes associated with generation of the user experiences according to an example implementation of the present application for the watchlist.

FIG. 9 illustrates user experiences according to an example implementation of the present application for a forecast analysis.

FIG. 10 illustrates processes associated with generation of the user experiences according to an example implementation of the present application for the forecast analysis.

FIG. 11 illustrates user experiences according to an example implementation of the present application for the forecast analysis.

FIG. 12 illustrates user experiences according to an example implementation of the present application for an alert chain.

FIG. 13 illustrates processes associated with generation of the user experiences according to an example implementation of the present application for the alert chain.

FIG. 14 illustrates processes associated with generation of the user experiences according to an example implementation of the present application for automated trading.

FIGS. 15-16 illustrates processes associated with generation of the mobile user experiences according to an example implementation of the present application for automated trading.

FIGS. 17-21 illustrate various example implementations.

FIGS. 22A-22B illustrate various example implementations.

FIGS. 23-24 illustrate various example implementations.

FIG. 25 illustrates an example environment according to an example implementation of the present application.

FIG. 26 illustrates an example computing environment with an example computer device suitable for use in some example implementations.

DETAILED DESCRIPTION

The following detailed description provides further details of the figures and example implementations of the present application. Reference numerals and descriptions of redundant elements between figures are omitted for clarity. Terms used throughout the description are provided as examples and are not intended to be limiting. For example, the use of the term “automatic” may involve fully automatic or semi-automatic implementations involving user or operator control over certain aspects of the implementation, depending on the desired implementation of one of ordinary skill in the art practicing implementations of the present application.

With a more complex and dynamic economy, there is a need for accurate data reflecting exactly what is going on in the economy at any given point in time. More specifically, in order to accurately determine the current state of the economy, and to then be able to determine present and future trends in the economy, accurate data is required so that the recommendation itself is accurate.

For example, when considering purchasing a particular stock, a purchaser such as a trader may consider corporate information related to the company associated with the stock. This corporate information may include, at a very high level, how much revenue a company is taking in, how much money the company lost for a particular period of time (e.g., quarter, month, year).

However, this general, broad data is often not an accurate depiction of how a company is actually behaving. For example, revenue for a clothing company may appear to be high overall, but when the data is broken down, the revenue may be coming from online sales primarily. Typically, stores with higher revenue from online sales end up closing several brick and mortar stores, because those stores are no longer profitable. Thus, a trader who is considering to buy that clothing company's stock may not want to purchase that stock if they know that those stores will likely close at a future point in time.

Unfortunately, without accurate data, a trader has little way of knowing how a particular trend will look in the future. Therefore, by collecting data and cleaning and normalizing that data, this cleaned, normalized data may be compared to historical data to determine how a particular trend will look in the future. Similarly, a trader may also not be able to assess present information, to make a decision or recommendation. According to the present example implementations, the cleaned, normalized data may be present data that is compared to historical data, to provide an analysis of current trends.

While the above example implementation describes determining trends related to the stock market, other metrics may be determined (e.g., obtained deterministically), including a regional, national, or universal unemployment rate, public and not public company revenues and market shares, consumer behavior across several companies, a basket of stocks (e.g., more than one particular stock such as an entire stock portfolio), electronic indices, restaurant indices, how particular sectors in the workforce are performing, inflation, and trends for mutual funds. In particular, any data or information which may have an economic impact may be measured.

Aspects of the example implementation are directed to apparatuses, methods and systems for receiving a plurality of data inputs from different data providers having different types of data. The different types of data are received in a big data system, which standardizes the data by performing normalization, de-duplication, and classification, and optionally other processes.

The standardized data is provided to a multi panel generator that builds a panel, builds a forecast, and generates a forecast. The forecast is output to an access point, where a user may access the forecast. The user experience may involve receiving the result of the forecast as a recommendation on a watchlist showing multiple entities, a detailed performance and recommendation report for one of the multiple entities, and/or an alert chain that provides the user with an alert that may be triggered by one or more conditions.

In the foregoing example implementation, the data is processed continuously and in real time, such that the user is automatically provided with real-time updates to the recommendations, watchlist and/or alert chain. The user may have the opportunity to execute a transaction, either manually or automatically, as well as to provide real-time feedback on the system.

To implement the foregoing example implementations, an architecture is provided, as explained in greater detail below. Further, the user experience associated with the architecture is also described in greater detail.

Architecture

As shown in FIGS. 1-3 , for example implementations described herein relate to an architecture, including system elements and associated functions, as well as operations.

FIG. 1 illustrates a schematic description of the architecture according to an example implementation. At 101, data is received from a plurality of alternate data providers. The details of the plurality of alternate data providers will be described below in greater detail. For example, but not by way of limitation, some of the data providers may include financial transaction information providers, location information such as GPS data, consumer behavior information such as social media or online publication information, or other data.

At 103, an automated tagging system is provided that receives the data from the plurality of data providers, and performs tagging, or labeling of the data. More specifically, the data may be standardized across the different types of data that were received from the different data providers. The standardization processes may include, but are not limited to, filtering, de-duplication, normalization, and classification or labeling. Further details of the automated tagging system are provided.

At 105, and updating and feedback process is provided. More specifically, manual or automatic processes may be provided for the automatic tagging system to be updated, and for checking and auditing of the process. Optionally, the input to the updating and supervising process may be provided to a manual source, such as a data miner or an analyst. Alternatively, in some example implementations an artificial intelligence system that employs machine learning, such as neural networks, may use back propagation techniques for periodic updates to the training phase.

At 107, financial data associated with a company is provided. More specifically, published information such as annual reports, press releases, information from the social media of spokespersons or executives, published pricing information, and other information as would be understood by those skilled in the art is provided.

At 109, the standardized data of the automated tagging system 103 and the company financial data 107 are provided to a modeling system 109. The modeling system 109 includes one or more handle generators and forecast builders, which are applied to a model. The model may include, but is not limited to an artificial intelligence-based system that applies machine learning, in the form of neural networks, to receive the standardized data of the automated tagging system 103 and the company financial data 107, apply them to the neural network, and generate, as an output, a forecast.

And as noted at 111, an input to the modeling system may include, but is not limited to, proprietary data associated with the merger and acquisition information of the company, and the fiscal quarters calendar of the company.

At 113, an output of the forecast is provided as one or more revenue predictions. As explained above, the company financial data that is based on the standardized data, as well as the proprietary data, is fed into the machine learning model to generate the revenue predictions.

At 115, a final output is provided in the form of a recommendation. For example, but not by way of limitation, the final output may be a recommendation to buy, hold or sell, as a transaction. Alternatively the final output may be a score. Still alternatively, the final output may be the execution of the transaction itself, without involving the user. Optionally, a rule-based or other deterministic approach may be employed, in combination with the probabilistic approach of the machine learning, as disclosed above.

FIG. 2 illustrates an architecture 200 according to the example implementations. Inputs 201 include data providers 201-207 provided to a big data system 211, which is in turn associated with an access point 213.

More specifically, as shown in 200, data is received as inputs 201 from a plurality of N data providers 203-207. Where the term “data source” is used herein, the data is acquired from one or more data provider, such as N data providers 203-209, as well as any other data providers as would be understood by those skilled in the art.

In the big data system 209, for each of the data providers 203-209, N corresponding adapters 215-221 are is provided. The adapters 215-221 may normalize 223, deduplicate 225 and classify 227 the data, as described herein.

As explained above, data is provided by the data providers 203-209, and processed by the data adapters 215-221. The output of the data adapters 215-221 is provided to an automatic tagging system, such that resulting output data has been normalized, de-duplicated and classified, as disclosed above. These aspects of the example implementations are automated; however, data miners and analysts may optionally supervise the process, and continue to update the process. The resulting output data may be combined with company financial data, such as financial reports or other publicly available information associated with characteristics of the company, either historical or present.

An output of the automatic tagging system and the company financial data is provided to a modeling system. The modeling system may include plural multi-panel generators 229, 231, 233, multi-forecast builders 235, 237, 239, and forecast modules 241, 243, 245. The modeling system generates, as its output forecast, a revenue prediction, based on financial data, proprietary data and machine learning. More specifically, the financial data and proprietary data includes the above described inputs of the automated tagging system and the company financial data. For example but not by way of limitation, the data may include financial reports, merger and acquisition information, and quarterly fiscal performance.

The output is the forecast, which may be provided in the format of a file, an API, a console or a custom format to the output. Accordingly, the output is provided to a user at the user access point. Example user experiences associated with the access point are described in greater detail herein.

FIG. 3 illustrates a process 300 associated with the foregoing structures and functions according to the example implementations. More specifically, the process is divided into a first phase 301 associated with data processing, a second phase 303 associated with development of the panel and calibration, and a third phase 305, associated with creating and applying a prediction model, and generating a forecast.

With respect to the first phase 301, at 307 input data is received. As noted above, and as explained herein, the input data is from a plurality of sources of different types. For example but not by way of limitation, the input data may include timeseries data from multiple vendors, such as credit card transactions, debit card transactions or other electronic purchase transactions.

At 309, the data is normalized. More specifically, the input data of operation 307 is mapped from the organic vendor data format in which it was received, to an internal data format that provides consistency across vendors. For example but not by way of limitation, the normalization involves accounting for the differences in the different alternate data sets, and standardizing that data to a common standard. Additional aspects may include the duplication or other processes to standardize the data.

At 311, brands associated with purchases are tagged. The tagging may involve the application of tagging rules on the normalized data. The rules may include, but are not limited to, rules that are specific to a credit card or debit card, geo-fencing rules for GPS data, rules associated with browser history or application usage, or other rules as would be understood by those skilled in the art. For example, but not by way of limitation, for a series of financial transactions, each of the financial transactions may be labeled, or tagged. To perform the tagging, one or more tagging rules 313 may be applied. The tagging rules may be considered to be an inclusive filter, or an exclusive filter. Further, in addition to a rule-based approach such as a filter, a natural language processing approach may be taken that incorporates artificial intelligence, such as machine learning models that involve neural networks.

Once the input data has been normalized and tagged, at the second phase 303, a panelization operation 315 is performed. According to the example implementations, a sample of users is established as a panel. The users are chosen to match criteria associated with the panel. For example, but not by way of limitation, the panel may be created in a manner that is associated with the input data churn rate. Other examples of channelization rules are shown at 317, and those rules may be based on user transaction patterns, census data balancing, or other rules that associate a characteristic of user transaction behavior with a transaction.

Once the panels have been generated at 315, a grouping process is performed at 319. More specifically, the panels are grouped by symbol. Brands associated with the data in the tagging process are assigned to symbols associated with a company. It is noted that this data may change over time, due to mergers, acquisitions, spinoffs, bankruptcies, rebranding, listing, delisting or other financial events. Thus, the events are assigned in real time to be included at the time of assigning the brand to the symbol at 319. The symbol may be chosen from a database, such as those shown at 321.

At 323, one or more corrections are applied to the grouped. For example but not by way of limitation, as shown in 325, patterns that are specifically associated with a financial institution are applied to calibrate the grouping. Examples of such patterns may include weekend postings of information, posting delays typically associated with a financial institution, as well as pending but not yet posted transactions. Additionally, as shown at 327, anomalies are removed. Examples of anomalies that are removed may include, but are not limited to anomalous transactions or anomalous users.

Once the panels have been fully generated in the second phase 303, the process proceeds to the third phase 305 as follows. At 329 a prediction model is generated. For example but not by way of limitation, in the training phase, historical data associated with a company, such as the fundamentals of the company and the stock price, as well as historical measurements that may have been previously were historically provided by the example implementations, are used as training data. Accordingly, the prediction model is trained based on this training data, as shown at 331.

At 333, a forecast is generated. Using the prediction model generated at 329, features associated with the open quarter 335 are applied, to derive a prediction of future stock price for future company fundamental metric. While the features are disclosed as being directed to an open quarter, example implement patients are not limited thereto, and other open periods may be substituted therefor.

The foregoing example implementations of the architecture may be run on the hardware as explained below with respect to FIGS. 26 and 27 . Further, the hardware provides for continuous large-scale data inputs, such that the model is continuously receiving data and be updated automatically and in real-time. Thus, the processing capability of the hardware must be sufficient to permit such processing. For example but not by way of limitation, a GPU may be used for the artificial intelligence processing. Alternatively, or in combination with the GPU (graphical processing unit), an NPU (neural processing unit) may be used. One or both of these units may be used in a processor that is located remotely, such as a distributed server system, for a cloud computing system.

For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources.

Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction.

Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

Alternative Datasets

As explained above, the architecture is configured to receive a plurality of alternative data sets. As shown in FIG. 4 , examples of the alternative data inputs 400, may include, but are not limited to, credit card transactions and debit card transactions for one, mobile device usage information 403, geolocation data 405, social data and sentiment data 407, and web traffic and Internet data 409.

The above-disclosed hardware implementations may be used to process the alternative datasets of FIG. 4 , as would be understood by those skilled in the art. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

FIG. 5 illustrates the processing of the alternative data sets according to the example implementations. More specifically, at 500, the receiving and processing of the alternative data sets is disclosed. The alternative data sets 501, may include, but are not limited to, data having alternative types. For example but not by way of limitation, GPS data 503, data associated with financial transactions 505, vaccination data 507, satellite image data 509, app usage data 511, and browsing history information 513 are all types of data that might be a part of the alternative data sets 501. However, the alternative data sets 501 are not limited to the foregoing example patients, and other data sets may also be included as would be understood by those skilled in the art.

At 515, the multiple sources of data have an ETL (extract, transform load) operation performed, to extract, transform and load the data. Accordingly, the features associated with the data types one through m at 515 are extracted into corresponding features one through m as shown at 517.

At 519, the process is subjected to a modeling operation. The modeling operation includes, as shown at 521, selection of the model, selection of the features, performing the training phase on the model, and performing model testing. The modeling operation 519 may be performed on an artificial intelligence system that uses neural networks and machine learning.

At 523, a validation step is performed, also known as backtesting. For example, the historical data associated with stock prices, company fundamentals, and historical decision or events, as disclosed at 525, are applied to the model that was generated. A determination is made, based on the validation of 523, whether the application of the historical information successfully validates the model. If the model was not successfully validated, or in other words the backtesting results were not found to be acceptable, the process returns to 519, and the modeling is again performed.

On the other hand, if the validation at operation 523 was successful, the operation proceeds. More specifically the operation proceeds to the modeling operation 527 and the forecasting operation 529, as discussed above.

The above-disclosed hardware implementations may be used to process the alternative datasets of FIG. 5 , as would be understood by those skilled in the art. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

Automatic Tagging

As the alternative data sets have been processed as explained above, and with respect to operation 101, automatic tagging 101 is performed on the data. FIG. 6 illustrates automatic tagging 600 in accordance with the example implementations.

At 601, the transactions are received and the alternate data sets are processed as explained above. At 603, normalization is performed. More specifically, features are extracted from the transactions that are relevant for the brand classifier.

At 605, brand classification is performed. More specifically, the extracted features of the normalization 603 are applied to a classification layered model. More specifically, a rule-based approach is applied that performs the extraction in a deterministic manner, and the rule based approach is mixed with an artificial intelligence approach, such as machine learning based on neural networks, that is probabilistic in nature. Accordingly, the brand classification 605 is performed in a mixed deterministic and probabilistic model.

At 607 a verification step is performed to verify that the classifier is accurate. More specifically, a sample of the classified data is verified, to confirm that the labeling was correctly applied with respect to the brand. If necessary, the classifier is retrained. Optionally, this verification and retraining operation at 607 may be performed iteratively, until the brand classification has been verified to a threshold confidence level.

At 609, the brands are classified with respect to companies. For example, the companies may be private companies, publicly, or other traded companies organizations having similar features to public or private companies. In a manner that is similar to operation 605 and 607 above, a mixture of rule-based, deterministic operations and probabilistic, artificial intelligence operations such as machine learning and neural networks, are employed so that the brands are classified to companies. Also similar to operation 607, at 611, the company classifier is verified to ensure that sampled data has been accurately labeled with respect to the classification of the company. If necessary retraining, and optionally iterative free training, may be performed until the company classification has been verified to a threshold confidence level.

At 613, once the brand classification 605 and the company classification 609 have been verified, the tagged transaction is considered to have been generated at 613. For example but not by way of limitation, the labeling is performed in a manner such that the data has been automatically labeled. An output of this process may be used in the panel generation, forecast building, and forecast.

The example implementations may have various advantages and benefits over the related art approaches. For example, but not by way of limitation, the related art approaches may suffer from problems or disadvantages, such as incorrect tagging of names that are common (e.g., DENNYS or SPRINT), names that are short (e.g., AMC or BOOT), names that are specific (e.g., TACO or TARGET), and names that are similar (e.g., FIVE BELOW or BIG FIVE). Further, entities may be omitted if they do not follow a clear standard. Examples of the lack of use of a clear standard resulting in company omissions includes the use of abbreviations instead of the full name, a change in the name over time, slight difference in names due a difference of timing of the acquisition of the store, or typographical errors in the name of the store. Other examples of related art errors include the assignment of the transactions to the wrong ticker (company indicia), even if the transactions clearly are associated with a different company.

The above-disclosed hardware implementations may be used to process the automatic tagging of FIG. 6 , as would be understood by those skilled in the art. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

User Experience

The outputs of the example implementations described herein may be provided in a user experience, in a manner that provides for the user to visualize information generated by the architecture. For example but not by way of limitation, a user may be provided with a watchlist that is generated to provide the user with decision-support information associated with the outputs of the architecture, such as a prediction, forecast, recommendation or the like. Additionally, detailed analysis of an entry on the watchlist may be provided, along with a specific recommendation, and detailed metrics regarding the basis of the recommendation, and optionally compared with a recommendation provided by an external benchmark. Further, the example implementations described herein may be used to provide a chain of alerts, or optionally, a decision support or automated decision tool, which combines a deterministic rules-based approach with the above described aspects, including but not limited to the art of artificial intelligence approaches.

Data processing associated with user experiences may be processed using the hardware disclosed herein. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

Watchlist

FIG. 7 illustrates a user experience associated with the example implementations. As shown at 700 the user experience provides a watchlist of companies, which may be selected by a user, for example, or suggested to the user based on preferences associated with the user. For example, but not by way of limitation, the watch list includes in a first column 701 a name of the company, including the company name and trading symbol. In another column 703, a stock price is provided, along with information on the performance, such as change in share price as total amount and percentage.

In yet another column 705, a type of critical data associated with the performance that is being used as an input in the example implementations is identified. As shown in FIG. 7 , the first row is associated with a first company, which may be a large retail company having physical and online presence for retail sales, for which the revenues is a critical indicator of performance. For the second row, which is an online subscription company, a number of other users associated with the product is a critical indicator of performance. For a third row, which is a retail restaurant that users may visit, same-store visits is provided as a critical indicator of performance. For a fourth row, which is a large automotive manufacturer, with international presence, US revenues is provided as a critical indicator of performance. For the fifth row, which is a social media company engagement of users (e.g., time spent on the platform) is provided as a critical indicator of performance.

In still another column 707, a performance associated with the critical indicator of performance is shown. As shown in FIG. 7 , for the first row the critical indicator of revenues are showing a performance increase of 0.4%; for the second row the number of users is showing an increase of 3%; for the third row, same-store sales is showing a decrease of 10%; or the fourth column, the US revenues are showing an increase of 6.2%; and for the last row, user engagement is showing an increase of 3%. Accordingly, the example user experience provides a user with information on a critical indicator of performance, as well as the actual performance based on the input data as explained above.

According to the present example implementations, based on the critical indicator and the performance, the system generates a score in yet another column 709. The score provides an indication for the user of the performance of the company, which the user can apply as a form of a recommendation. For example, but not by way of limitation, in the case of the first row in FIG. 7 , a growth of 0.4% revenue is associated with a score of neutral, whereas in the second row, an increase in the number of users of 3% is associated with over performing. In the third row, a 10% decrease in same store sales is associated with an underperforming score. In the fourth row, an increase of 6.2% in US revenues is associated with an over performing score. In the last row, an increase of 3% engagement is associated with an over performing score.

Accordingly, the user experience according to the example implementations provides the user with information on the critical indicator of performance, which is determined by the system based on the type of company and the available data among the plurality of the data streams. Further, the actual performance of the critical indicator for each of the companies is provided, along with a determination of the score. For example, but not by way of limitation, the information of the first row, such as revenue information may be generated based on the input credit card information that is received as a data source, as explained elsewhere in this disclosure. That information may be used to determine a revenue associated with the company, and may be used to calculate the performance.

While the score shown in the drawings is a single word, such as neutral, over performing or underperforming, other scores may be substituted without departing from the inventive scope. For example, but not by way of limitation, a numerical score, such as a performance rating from 1 to 10, may be provided. This information and score is generated based on the input data that is provided, as well as observations of what is characterized as an appropriate score relative to that company. Thus, each company may have a different score determination based on company attributes such as industry or company size, to determine the amount of variation in performance that is necessary to provide the score.

The example implementations described herein provide a method of determining a critical indicator, as shown in the watchlist. For example, but not by way of limitation, historical data may be applied in an artificial intelligence machine learning model in order to determine the criteria having the highest correlation with respect to a change in the stock price. For example, but not by way of limitation, some related art approaches may attempt to directly measure a grossed number of users in order to determine revenue. However, such related our approaches can be accurate, because a doubling of the number of users does not necessarily correlate to a doubling of the amount of revenue. The reason this may be true is because the new users may not have the same representation, use pattern or consumer preferences as the initial or earlier users.

Similarly, the geographical location of use, users or other information is crucial to determining whether the data is representative of the users, and can correctly determine the critical indicator. As explained above with respect to the example implementations, GPS data is received as an input, and is also stabilized in the automated tagging system, so that the data can be representative. As another example, the data must be stabilized not just to show the overall number of users, but to show the amount of time that a user spends in an online app, because if the new user spends more time or less time in the app than the current users, this may be reflective of a different user behavior with respect to revenue, purchase, advertisements or the like, and can make the data more accurate.

In a similar manner, when a company acquires a target, the number of users may increase, although those new users may not be representative of the earlier users. During the time between the announcement of the merger and the completion of the merger process, several months or years may pass, during which publicly available information may be incorporated into these example implementations and thus adjust the critical indicator, performance indications, and or recommendations to calibrate for such information. Legal or regulatory blockages, such as antitrust or export control, may stall or block the merger, such that the presence of certain terms in publicly available information associated with the merger can be used to adjust the forecasting and recommendation. Further, the predictive aspect of the tool may provide a forecast for performance after the merger, based on similar patterns that were used to train the model as to how to characterize, process and generate an output prediction for such models.

As another example, for a stock associated with the restaurant, the change in pandemic status of the coronavirus from a more severe situation to a less severe situation may influence consumer preference to return to in person dining. The inclusion of such information may be more sensitive for certain industries or companies. In the case of coronavirus, the industries of travel, leisure, dining or others may be more sensitive as compared with other industries; the present example implementations are capable of performing data stabilization to account for such changes. Without the foregoing approaches of the example implementation which performed normalization, the duplication, classification and data stabilization, the data lacks the necessary accuracy to determine the critical indicator with a sufficiently high degree of confidence (e.g., clustering to better represent the user population).

FIG. 8 illustrates a process for generating and updating information to the watch list, in accordance with the example implementations. As it relates to the user experience described above, the type of critical indicator as well as the score are continuously updated based on data inputs, on a real-time basis. For example, in the first row revenue is listed as a critical indicator type. However, if there are changes in the incoming data associated with the company, the example implementations may change the type of critical indicator from revenue to another critical indicator, such as same-store sales, customer base, or other critical indicator.

More specifically, as shown at 800, inputs are provided into the architecture described herein. For example, but not by way of limitation, there is a separate pipeline for each type of signal associated with a critical indicator, for each company. Thus, in the above described example, for the first company, there may be multiple pipelines for each of the candidate critical indicators. One pipeline may be associated with the signal for the revenues, and another may be associated with consumer spending, or indicators of company performance.

More specifically, at 801 real-time data events from alternative data sources, as explained above are provided. Each of the pipelines is triggered by receiving new data that is relevant to the model. The input of new data from alternate data sources is described as explained above. These real-time data events are processed according to the example implementations with respect to the architecture to generate a signal based on the current data. Thus, an updated signal is provided at 803. More specifically, the new data that was received at 801 is provided to the model of the example implementations. Accordingly, a prediction is generated as described above, and is provided as an output signal.

At 805, a strength of the updated signal is evaluated. For example but not by way of limitation, the output signal, which may be a prediction of the potential critical indicator, is compared with benchmark consensus signals. According to one example implementation, the updated signal may be a predicted revenue for a company, which is compared with a prediction generated by one or more analysts, or an analyst consensus, from available information. Based on the comparison between the updated signal and the benchmark signal, a signal strength vector is generated, which is indicative of a relative degree of closeness between the updated signal and the benchmark signal.

At 807, the strength of the updated signal is classified. More specifically, the signal strength vector generated at 805 is classified into a recommendation. For example but not by way of limitation, the recommendation may be a one-dimensional actionable recommendation, such as hold, buy or sell.

At 809, the classification associated with the strength of signal is used to generate any updates, which are subsequently provided and displayed to the user in the user experience. More specifically, the user interface, such as the web interface, a mobile interface, or a pushed alert may be updated with the results of the signal strength classification, as well as the watchlist update. Thus, according to an example implementation, the user may be provided with a change in the critical indicator type, as well as a change in the recommendation, depending on which of the pipelines has the strongest vector. Optionally, plural pipelines may be blended or weighted based on the signal strength, to provide the blended result, with the critical indicator being listed as the most heavily weighted indicator. According to another example implementation, plural indicators may all be listed, along with plural outputs of the results, followed by a recommendation based on a matrix operation or multiplexing of the strength vector, weighted or unweighted, associated with each of the pipelines for each of the signals for each of the companies.

According to this example implementation, the user may be provided with real-time changes in critical indicator, performance and recommendation that are actionable. As explained below, the recommendations may also be provided in the detailed analysis of a company, or a chain of alerts and may be used for the recommendation or actual action automatically being taken.

The above-disclosed hardware implementations may be used to process the watchlist of FIGS. 7-8 , as would be understood by those skilled in the art. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

Performance and Recommendation

As shown in FIG. 9 , according to another example user experience 900, any of the companies shown in the foregoing user experience of FIG. 7 may be selected for providing a further summary. Here, the fourth row is selected, and further information associated with the forecast is provided. A recommendation 905 is provided, in this case “strong buy” based on a decrease in the revenue.

Further details 903 are provided to the user, such as the relative impact of revenue on the stock price (e.g., correlation between revenue and stock price), and the prediction accuracy for the stock associated with the example implementations. Information on the forecast based on the analyst expectation is provided, in comparison to the forecast based on the real data measurement, as well as the score associated with the performance that is based on the real data measurement. Charts 907 are provided showing a comparison of the revenue based on real data measurement, as compared with the expected revenues, which may be based on published information that was provided by the company. Additionally, information of the stock prices also provided.

FIG. 10 illustrates a process 1000 for generating an output that visualizes a difference between expected values and actual values according to the example implementations.

At 1001, measured sales are provided. First applicable not by way of limitation, as disclosed above, the measure sale may include company sale that are calculated, such as in the second phase 303 as shown in FIG. 3 , and disclosed above.

At 1003, expected sales are provided. The expected sales may be based on analyst prediction, analyst consensus, industry publication, or other available information associated with the providing of expected sales information, as opposed to actual sales information.

At 1005, for the measured sales obtained at 1001, and aggregation operation is performed. More specifically, the measured sales are aggregated based on time series into intervals that are comparable with interval associated with the expected sales signal. For example but not by way of limitation, if the expected sales signal has a known time interval such as daily, weekly, hourly, quarterly, etc., the measured sales are aggregated into comparable time periods.

At 1007, a scaling operation is performed. More specifically, because the measured sales provide information from a sample of the population, the measured sales need to be scaled. For example but not by way of limit deletion, the scaling may involve extrapolating a sample representative population associated with the sample, and similarly to extrapolation of the aggregated sales of that population of the sample to the representative population.

At 1009, the periods associated with the scaled, aggregated information of measured sales from 1001, 1005 and 1007 are aligned with the period of the expected sales of 1003. Accordingly, the aggregated, scale measured sales are joined with the expected sales, by time interval.

At 1011, a visualization operation is performed. Accordingly, an output may be provided to a user in the form of a bar plot 1013, a line plot 1015 or any other visualization technique 101 7th as would be understood by those skilled in the art. Visualization techniques are not limited to a single approach, and different visualization techniques may be combined, appended, mixed or blended. Further, instead a graphic visualization approach, a text output may be provided in the form of a narrative chart that simply displays the result.

FIG. 11 illustrates an example graphical visualization associated with the example implantations described above. More specifically, at 1100, a chart is provided that displays sales revenue on a weekly basis over a 12 week period. At 1101, the aggregated information of the measured sales, which has been aligned to a weekly period, is displayed. Additionally, at 1103, the expected sales, provided on a weekly interval, is displayed. Accordingly, a user may be provided with a display that illustrates a difference between the measured sales as associated with the example implementations herein, and the expected sales, as provided by analysts, analyst consensus, etc.

Returning to FIG. 9 , the charts 907 include a revenue comparison. Thus, the user can visualize, and understand by looking at the detail information and 903, that the measured revenue is about 6.2% higher than the forecast based on the expectation by the analysts. Thus, the example implementations provide a determination that the entity is over performing as compared with the analyst expectation. As a result, the example implementations generate a recommendation of “strong buy” at 905, in the manner explained above.

The above-disclosed hardware implementations may be used to process the evaluation and recommendation operations associated with FIGS. 9-10 , as would be understood by those skilled in the art. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

Alert Chain

As shown in FIG. 12 , according to yet another user experience associated 1200 with the example implementation, alerts are provided to the user. The selected alerts are listed in rows, divided into the alerts specific to the user 1201 and an aggregated list of the most popular alerts 1213 across all of the users. As previously disclosed, a column is provided for the name and stock symbol of the company, as well as the type 1203 of information that is the basis for the alert, the condition 1205 that triggers the alert, and the frequency 1207 of the alert to be provided. The user is provided with a tool 1209 to set the alert to active or inactive, to a tool 1211 to edit the alert, and to delete the alert.

For example but not by way of limitation, as shown in the first row, the alert may be based on the performance being greater than 5%. As shown in the second row, plural alerts are provided to be associated with a single company, in this case the price moving above 5% and the score having a value of “over performing”. Similarly, a time-based alert may be provided, such as the user being provided at an alert 10 days before an earning call, as shown with respect to the third row. Accordingly, the user is provided with a chain of alerts that may be triggered by one or more conditions associated with a company.

As also shown in FIG. 12 , users may be able to view the most popular alerts 1213 that are being generated across the user base, as well as the number of users 1215 that are generating and using those alerts. Detailed information such as type, condition and frequency each of those popular alerts is provided. The user is provided with an option to add those alerts to their own user alert chain as shown by the “+” symbol 1217.

FIG. 13 illustrates operations 1300 associated with the processing of the chain of alerts. For example, as explained above, a type, condition, performance, price and score can be processed as data, to determine whether to provide the user with an alert. Further, the user may view and consider the alerts being used by the overall community of users, to benefit from alerts generated by others. According to the example implementations, the user may subscribe to such a rule, and thus be alerted in response to changes in the signals described above.

At 1301, a signal update is performed. More specifically, as explained above with respect to FIG. 8 at 803, signal updating is performed. For example but not by way of limitation, and output of the watchlist may be provided, including but not limited to the signal strength vector and the signal strength classification.

At 1303, the output of 1301, such as the absolute values of the signal, or relative values of a signal as compared with the previous signal update are applied to the deterministic rules. For example but not by way of limitation, if a revenue has increased by 2% as compared with the previous signal update, and the user set a rule to provide an alert when the revenue has increased by 2% or more for a given company, the rule may be triggered. Similar or other deterministic rules, as disclosed above with respect to FIG. 12 , are processed in real time as the updated information of 1301 is provided. Accordingly, the probabilistic output of the watchlist is applied to the deterministic rule base of the user, and an alert is either triggered or not triggered with each real-time update.

At 1305, a notification generation operations performed. More specifically, based on the user rule-based, a custom notification payload is generated for the user. For example but not by way of limitation, if a user has determined that for a revenue that has increased by 2% or more compared to the previous signal update, the user should receive an alert to sell a stock cut, such a notification payload is generated.

At 1307, the notification is distributed to the user. The distribution channel may be set to one or more modes, including but not limited to mobile application notification, email, simplified messaging service, or other communications means. Accordingly, a notification is pushed to a user in the desired manner of the user, containing the recommendation associated with the rule, which is triggered based on the real-time signal update provided to the rule-base.

While some example implementations may provide a recommendation, in real time, based on the real-time measurement of data collection, price checking and calculation, to provide the addition, the example implementations are not limited to recommendations. The foregoing example implementations may be integrated with approaches that provide for automatic trading, such that the user need not provided input for and execution of a decision.

FIG. 14 illustrates a process 1400 associated with decision execution according to the example implementations. More specifically, instead of the user receiving and reviewing the signal classification and signal strength vector to receive an alert, an automatic system is provided that applies artificial intelligence techniques such as machine learning in a neural network to convert the signal classification and signal strength vector into a decision signal that can be submitted for execution of the decision. For example but not by way of limitation, the signal may be converted to a trading order for a brokerage service.

At 1401, in accordance with the foregoing example implementations, measured data is received from a plurality of alternate data sources, and processed on a real-time, automatic basis to provide real-time updates for the critical indicators.

At 1403, the updates are input into a trading model equal but not by way of limitation, the trading model may include an artificial intelligence approach such as machine learning in a neural network to provide trading decision-making. According to an example implementation, the trading model may be a neural network that is trained on historical stock prices and a history of signal updates associated with the measured signal according to the example Tatian. The input to the trading model is the signal data, and the current state of the user account. For example, if the user has open or pending orders associated with a purchase or sale, the model takes this information into consideration. As an output, the trading model 1403 provides a decision or an action, instead of an alert or a recommendation as is done in other example implementations.

At 1405, an order is created. For example, the order may be created by submitting an automated request to a seller, including but not limited to a brokerage service, and optionally confirming the order with the user. For the user confirmation, this may optionally be provided by a notification distribution channel, as explained above with respect to FIG. 13 .

At 1407, the system performs an operation to determine whether user review is required. If no user review is required, the order is executed at 1409. For example, the order created at 1405 may be executed with a seller, such as a brokerage service. Alternatively, if at 1407 it is determined that user review is required buyer, the confirmation request is sent at 1411, as explained above through a notification distribution channel. If the user confirms the order at 1411, the order is executed at 1409. If the user does not confirm the order of 1411, the order is considered to be rejected, and cancel at 1413.

At 1415, an operation is performed to update the user portfolio, so as to indicate that the order has been executed. Optionally, the user may be provided with a report via the communication or distribution channels explained above, to confirm that the order was executed, to provide an update of the portfolio, and/or to remind the user of any pending or open orders.

The above-disclosed hardware implementations may be used to process the alert chain disclosed in FIGS. 12-14 , as would be understood by those skilled in the art. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

The foregoing example implementation of the automatic trading aspects is performed continuously and in real time. Thus, plural orders may be simultaneously executed, or may be in different stages of execution. To the extent that confirmation by the user is requested, the user may decide to execute some orders, reject other orders, and to not make it make patient keep still other orders pending. To the extent that confirmation is not required by the user, automatic execution may continue without providing the user with any review prior to the execute acute the notification of pending order or current portfolio immediately after the execution. Implementation, when review is not required by the user, another subject that is not military. A require, a change in availability on, that is the identity for justice, or that of entity side of order exceeds a prescribed on individual or periodic purchase amount.

The foregoing example implementations automatically perform a determination of the critical indicator type, provide a calculation of performance, and generate a score, for each of the listed companies. For the foregoing example implementation of the user experience, determination of the leading indicator, and comparison of performance is provided on a real-time basis. As explained above, a mixture of rule-based, deterministic approach is blended with a probabilistic approach, such as the artificial intelligence neural network approaches described herein. The architecture may be executed on a big data server, such as in a server farm or in the cloud. Accordingly, the signals are processed as they are received, in real-time, in contrast to related art approaches, which perform batch processing. Further, cloud computing may also be used. To the extent that the necessary processing power is available, the signal processing associated with the example implementations may be performed on a standalone machine. Due to the present example implementations being able to provide real-time information, a user may be able to receive the recommendation and execute a decision in a timely manner that provides for a significant impact on the return on investment. In contrast, related art approaches do not take into consideration the processing of the real-time measured data, instead only use expected data information.

While the foregoing example implementations are shown on a screen of a display such as a laptop or desktop computer, the example implementations are not limited to the or two in terms of the user experience. For example but not by way of limitation, a user experience associated with a mobile device may be substituted for or used in combination with the foregoing example user experiences. FIGS. 15-16 illustrate such example implementations associated with a mobile device.

The foregoing example implementations may also be used to provide users with a discount for goods and or services associated with a company. The discount may take the form of a rebate, a reward, a price reduction or other form of benefit or compensation to a user. For example but not by way of limitation, the discount may be provided to a user based on the amount for number of transactions by the user on the account of the company shown in the example user experience, for which the example implementations are performing the foregoing operations on the foregoing structures.

Optionally, according to the example implementations, a feedback loop may be provided. More specifically, a user may provide input on the outcomes and recommendations of the model, which may be used to calibrate the model. For example, but not by way of limitation, if, based on the critical parameter or indicator, combined with a performance, a recommendation has been set with which the user disagrees, the user may provide a suggestion for feedback into the system. The user may suggest that the critical indicator is not appropriate, and instead suggest another critical indicator, as well as being able to suggest that the recommendation is not a desirable recommendation. According to one example implementation, a user may indicate that an appropriate critical indicator of social media or an online service may not be user engagement or number of users alone, but may instead be related to online advertising, clicks or some other parameter. This feedback may be used by the system to retrain or recalibrate the forecasting tools, so as to adjust according to consumer preferences and demands.

Optionally, an automated trading tool may be provided that implements certain recommendations under certain circumstances. For example, but not by way of limitation, for items on the watchlist that are also on the alert chain, the instruction from the user in the user preferences may indicate that a particular stock should be bought or sold when one or more of the conditions in the alert chain have been met. Optionally, the user may create a completely different and separate alert chain for automatically trading, as well as for providing alerts. Thus, sales and purchases may be executed by the user automatically, thus avoiding any delay, and immediately providing such instruction. Such a system may be valuable during certain use cases. For example, but not by way of limitation, the automated trading tool could be valuable when the user is traveling or on vacation, during peak periods of activity or intense financial news, such that the user cannot quickly or in a timely manner act on alerts or recommendations, or simply for user convenience.

Also optionally, in addition to the company financial data being used as explained above, other publicly available data associated with a company may also be used. For example, but not by way of limitation, the public facing announcements, social media posts, public presentations, or other information may be sensed or detected for leaders of a company associated with one or more social media accounts, industry events, news releases or publications, or other information. This information may in combined into the sentiment analysis.

The foregoing example implementations may have various advantages and/or benefits. For example, but not by way of limitation, the example implementations may provide a way of determining performance automatically and in real time. Related art approaches may conduct manual research and generate performance indication manually over a period of many hours in many days, and an investment advisor may manually determine a score. However, the related art approaches do not have any way of taking disparate data from different data sources, performing operations on the data such as normalization, de-duplication, classification and optionally others, applying the refined data to a forecasting tool, and generating a forecast or recommendation based on a determination that a particular indicator is critical, all automatically and all in real time.

This distinction is crucial, because the information and recommendations must be provided in real time in order for a user to be able to effectively make decisions and execute the decisions in a timely manner, before the forecast has again changed due to the passage of time, the dispersion of information, new information or other events. The real-continuous determination and recalculation and re-forecasting provides information and recommendations that is precise, accurate and available for decision support to the user.

Data Cleaning and Pipelining

According to the foregoing example implementations, users are sourced to create a panel. As provided herein, a panel may be selected according to the following selection process.

An optimal panel to be used for forecast may be generated. More specifically, the selection process includes performing a filter operation on the candidate users for the panel. For example, but not by way of limitation, the filter operation may be performed by the application of a filter, so as to generate a panel meeting one or more criteria. According to the present example implementation, the criteria may include, but are not limited to, the panel including users that are representative of a population (e.g., US population) for their geolocation, with a substantially stable number of purchases from a starting date to an ending date (e.g., 2011 to the current date), with a consistent number of transactions. Optionally, outliers and duplicates may also be removed.

As shown in FIG. 17 , a selection process 1700 may be performed. Initially, the pool of candidate users is a fragmented panel consisting of 60 million users at 1701. After a first filter process performs the filtering operation such that the pool of candidate users is representative of the population for their geolocation, the filtered pool is narrowed to 15 million users at 1703. Subsequently, another filter operation is performed to confirm a stable number of purchases over a time interval, further narrowing the pool of candidate users to 4 million users at 1705. At 1707, outliers and duplicates may be removed, and a filter operation may be performed for a consistent number of transactions, to produce an optimal panel of 1.5 million users.

FIG. 18 illustrates a data pipeline according to an example implementation. At 801, data normalization is performed. Data that is received from different institutions may have different structures. In order to properly use the data from the different institutions, the data must be normalized with a fixed format. More specifically, the data is transformed from a text format into a distributed database that is designed to operate on top of the transactions.

At 1803, a data cleaning operation is performed. More specifically, the data that is not required or desired for the data processing pipeline 1800 is removed. For example but not by way of limitation, duplicated transactions, duplicated accounts and duplicated users are identified and removed. Further, incomplete data, such as incomplete transactions with missing data, are also removed from the data. Accordingly, and as explained above with respect to panel selection, the base of users that follows the selection process and filter operation is maintained in the user database, and the outliers and duplicates are removed.

After the data cleaning 1803 has been completed, a classification operation 1805 is performed. In this operation, each of the transactions in the database is classified. The classification is performed by analyzing the description of the transaction, and associating a correct merchant name with the description. In this operation, the quality of the association directly and critically influences the quality of the correlation and rejections that will be described further below. More specifically, to reach a desired accuracy, such as close to 100%, a combination of automated machine learning algorithms is combined with manual human controls.

As an example of the foregoing classification operation 1805, an example extract is provided. According to one example implementation, an average monthly volume of processing may be more than 200 million transactions; each of those transactions must be associated with a correct company.

FIG. 19 illustrates the example extract. As can be seen in the example extract 1900, the name of the merchant is found in each of the transactions.

Once the cleaned data has been classified as explained above, a modeling operation 1807 is performed. More specifically, the modeling operation 1807 generates forecasts. As inputs, the modeling operation 1807 applies data output from the classification 1805, as well as third-party input, for example Bloomberg data 1809. In the modeling operation 1807, many forecasts are combined, to obtain an optimal results. The modeling operation 1807 is specialized to a category associated with the company. Further, the modeling operation 1807 compensates for various bias factors, such as seasonality and the like.

FIG. 20 illustrates an example implementation 2000 associated with the modeling operation 1807. More specifically, a plurality of sets of panels 2001, subject to the foregoing operations of the data pipeline 1800, are provided to the plurality of corresponding sets of forecasts 2003; outputs of the sets of forecasts 2003 are provided to plural assemblers 2005, to generate a final forecast 2007.

In the modeling operation 1807, different categories of companies may require different algorithms to generate the forecasts. For, but not by way of limitation, the algorithms must incorporate the different behavior of consumers for the different structures of revenue within a company. Some of the categories may include, but are not limited to, fully owned restaurants, franchise restaurants, supermarket chains, insurance, and other companies.

The modeling operation 1807 also provides for bias correction. For example but not by way of limitation, the panel data may include historical data of several years, from thousands of users that shared their data in exchange for a token or reward. Such an approach to obtaining the data allowed for a more complete understanding of the bias impacted by the panels that are not randomized, and algorithms for the correction of the bias.

FIG. 21 illustrates a user experience 2100 associated with obtaining the information. At 2101, a user is provided with an input screen to input data and enter a referral code, as well as a number of points that may be associated with completing the survey. At 2103, the completion of the survey by the user results in the number of points being increased, and an option for selection of a bank where the points may be deposited, as well as a privacy statement.

To perform bias correction, historical data points are analyzed, to determine how the bias behaves across time. According to one example implementation, 9 algorithms were created for adjusting the bias in the data. Then, those 9 algorithms were combined with three other algorithms that are used for tickers, and that are less impacted by the bias.

At 1811, an output of the modeling is provided to make predictions. More specifically, the data is aggregated and inserted in a database. The data in the database can be accessed and used by other rules, such as traders, and further retrieved for validation, back testing, etc.

Additionally, the data pipeline 1800 includes anomaly detection 1813-1819. More specifically, an output of each of the elements of the data pipeline is subject to anomaly detection, to identify anomalies that may compromise final predictions. As an example of the anomaly detection 1813-1819, dataflow anomalies in the pipeline chain may examine technical anomalies as well as data anomalies.

For example, but not by way of limitation, anomalies in the behavior of a company for which forecasting is being performed may be analyzed and provided, including, but not limited to the following:

1. Acquisitions or divestitures, sourced from third-party news sources

2. Changes in requirements that would result in different company behavior, such as accounting standards, sourced from, for example, but not by way of limitation, SEC (Securities and Exchange Commission) files.

3. Change in a ratio between franchisees and stores owned individually

4. A different duration of a quarter, such as changing from 90 days to 97 days

5. Special sales promotions or other promotional activities for weeks, which may vary from quarter to quarter

6. Releases of new products by companies.

According to an example implementation, representativeness is considered. More specifically, according to a specific example, in 2019 the US population was about 330 million individuals, with the average family size being 3.14 members, such that there are roughly 105 million families, some studies indicating the number to be as high as 128 million families. In the example implementations, the ratio between the number of US households and the best panel is roughly 70 to 85. Further, the ratio between the declared revenues of companies and the total amount of purchases in the panel is between about 70 and 90. This ratio is consistent with the expected value, and is consistent across different companies, such that the proportion of consumers is properly maintained the panels according to example implementations.

FIGS. 22A and 22B illustrate various examples of comparison with data. FIG. 22A includes franchising examples, and FIG. 22B includes examples of companies with a history of acquisitions, or anomalies.

FIG. 23 illustrates a comparison between results according to the example implementations and the related art approaches. As can be seen in the column indicated as “DF” for the example implementations, and “1010 Data” for the related art approaches, a substantial difference in the forecasting results shows substantially improved performance for the example implementations.

FIG. 24 illustrates the technical basis according to statistical methods for the determination of the panel size, and the measurement of the real statistical error.

From the central limit theorem, the theoretical % error for the forecast is given by

$E\%{\propto {\frac{1}{\sqrt{N}}\frac{s}{\overset{¯}{x}}}}$

The Error % in the forecast is proportional to the sample standard deviation of the purchases and inverse to the square root of the purchase number and the average amount.

That means that the panel size is adequate to generate accurate predictions.

The real statistical error is even smaller, because we use the previously released revenues to correct and adjust the data.

The above-disclosed hardware implementations may be used to process the operations of FIGS. 18-24 , as would be understood by those skilled in the art. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

Example Environment

FIG. 25 shows an example environment suitable for some example implementations. Environment 2500 includes devices 2510-2555, and each is communicatively connected to at least one other device via, for example, network 2560 (e.g., by wired and/or wireless connections). Some devices may be communicatively connected to one or more storage devices 2540 and 2545.

An example of one or more devices 2510-2555 may be computing devices 2600 described in FIG. 26 , respectively. Devices 2505-2555 may include, but are not limited to, a computer 2510 (e.g., a laptop computing device) having a monitor, a mobile device 2515 (e.g., smartphone or tablet), a television 2520, a device associated with a vehicle 2525, a server computer 2530, computing devices 2535 and 2550, storage devices 2540 and 2545, and smart watch or other smart device 2555.

In some implementations, devices 2510-2525 and 2555 may be considered user devices associated with the users of the enterprise. Devices 2530-2550 may be devices associated with service providers (e.g., used by the external host to provide services as described above and with respect to the collecting and storing data).

The above-disclosed hardware implementations may be used in the environment of FIG. 25 , as would be understood by those skilled in the art. More specifically, For example, but not by way of limitation, external data fetching according to the example implementations described herein may be performed by copying data from an external third party (e.g., vendor), and storing the data in a cloud storage container. The data fetching process may be managed by a scheduling server, and/or a serverless compute service that executes operations to manage the external data storage and the associated compute resources. Further, the extraction, transformation and loading of data as described herein may be executed by a batch management processor or service. Batch computing is the execution of a series of executable instructions (“jobs”) on one or more processors without manual intervention by a user, e.g., automatically. Input parameters maybe pre-defined through scripts, command-line arguments, control files, or job control language. A batch job may be associated with completion of preceding jobs, or the availability of certain inputs. Thus, the sequencing and scheduling of multiple jobs is critical. Optionally, batch processing may not be performed with interactive processing. For example, the batch management processor or service may permits a user to create a job queue and job definition, and then to execute the job definition and review the results. According to an example implementation a batch cluster includes 256 CPUs, and an ETL-dedicated server having 64 cores and 312 GB of RAM. The number of running instances may be 1. The foregoing ETL infrastructure may also be applied to the process of insight extraction. Further, an API is provided for data access. For example but not by way of limitation, the REST API, which conforms to a REST style architecture and allows for interaction with RESTful resources, may be executed on a service. The service may include, but is not limited to, hardware such as 1 vCPU, 2 GB RAM, 10 GB SSD disk, and a minimum of two running instances. The API may be exposed to the Internet via an application load balancer, which is elastic and permits configuration and routing of an incoming end-user to applications based in the cloud, optionally pushing traffic across multiple targets in multiple availability zones. The caching layer may be provided by a fast content delivery network (CDN) service, which may securely deliver the data described herein with low latency and high transfer speeds. According to the example implementations, containers may be run without having to manage servers or clusters of instances, such that there is no need to provision, configure, or scale clusters on virtual machines to execute operations associated with containers.

Example Computing Environment

FIG. 26 shows an example computing environment with an example computing device suitable for implementing at least one example embodiment. Computing device 2605 in computing environment 2600 can include one or more processing units, cores, or processors 2610, memory 2615 (e.g., RAM, ROM, and/or the like), internal storage 2620 (e.g., magnetic, optical, solid state storage, and/or organic), and I/O interface 2625, all of which can be coupled on a communication mechanism or bus 2630 for communicating information. Processors 2610 can be general purpose processors (CPUs) and/or special purpose processors (e.g., digital signal processors (DSPs), graphics processing units (GPUs), and others).

In some example embodiments, computing environment 2600 may include one or more devices used as analog-to-digital converters, digital-to-analog converters, and/or radio frequency handlers.

Computing device 2605 can be communicatively coupled to input/user interface 2635 and output device/interface 2640. Either one or both of input/user interface 2635 and output device/interface 2640 can be wired or wireless interface and can be detachable. Input/user interface 2635 may include any device, component, sensor, or interface, physical or virtual, which can be used to provide input (e.g., keyboard, a pointing/cursor control, microphone, camera, Braille, motion sensor, optical reader, and/or the like). Output device/interface 2640 may include a display, monitor, printer, speaker, braille, or the like. In some example embodiments, input/user interface 2635 and output device/interface 2640 can be embedded with or physically coupled to computing device 2605 (e.g., a mobile computing device with buttons or touch-screen input/user interface and an output or printing display, or a television).

Computing device 2605 can be communicatively coupled to external storage 2645 and network 2650 for communicating with any number of networked components, devices, and systems, including one or more computing devices of the same or different configuration. Computing device 2605 or any connected computing device can be functioning as, providing services of, or referred to as a server, client, thin server, general machine, special-purpose machine, or another label.

I/O interface 2625 can include, but is not limited to, wired and/or wireless interfaces using any communication or I/O protocols or standards (e.g., Ethernet, 802.11x, Universal System Bus, WiMax, modem, a cellular network protocol, and the like) for communicating information to and/or from at least all the connected components, devices, and network in computing environment 2600. Network 2650 can be any network or combination of networks (e.g., the Internet, local area network, wide area network, a telephonic network, a cellular network, satellite network, and the like).

Computing device 2605 can use and/or communicate using computer-usable or computer-readable media, including transitory media and non-transitory media. Transitory media include transmission media (e.g., metal cables, fiber optics), signals, carrier waves, and the like. Non-transitory media include magnetic media (e.g., disks and tapes), optical media (e.g., CD ROM, digital video disks, Blu-ray disks), solid state media (e.g., RAM, ROM, flash memory, solid-state storage), and other non-volatile storage or memory.

Computing device 2605 can be used to implement techniques, methods, applications, processes, or computer-executable instructions to implement at least one embodiment (e.g., a described embodiment). Computer-executable instructions can be retrieved from transitory media, and stored on and retrieved from non-transitory media. The executable instructions can be originated from one or more of any programming, scripting, and machine languages (e.g., C, C++, C#, Java, Visual Basic, Python, Perl, JavaScript, and others).

Processor(s) 2610 can execute under any operating system (OS) (not shown), in a native or virtual environment. To implement a described embodiment, one or more applications can be deployed that include logic unit 2655, application programming interface (API) unit 2660, input unit 2665, output unit 2670, service processing unit 2690, and inter-unit communication mechanism 2695 for the different units to communicate with each other, with the OS, and with other applications (not shown). For example, alternate data processing unit 2675, tagging unit 2680, and modeling/forecasting unit 2685 may implement one or more processes described above. The described units and elements can be varied in design, function, configuration, or implementation and are not limited to the descriptions provided.

In some example embodiments, when information or an execution instruction is received by API unit 2660, it may be communicated to one or more other units (e.g., logic unit 2655, input unit 2665, output unit 2670, service processing unit 2690). For example, input unit 2665 may use API unit 2660 to connect with other data sources so that the service processing unit 2690 can process the information. Service processing unit 2690 performs the filtering of panelists, the filtering and cleaning/normalizing of data, and generation of the results, as explained above.

In some examples, logic unit 2660 may be configured to control the information flow among the units and direct the services provided by API unit 2660, input unit 2665, output unit 2670, alternate data processing unit 2675, tagging unit 2680, and modeling/forecasting unit 2685 in order to implement an embodiment described above. For example, the flow of one or more processes or implementations may be controlled by logic unit 2655 alone or in conjunction with API unit 2665.

Although a few example implementations have been shown and described, these example implementations are provided to convey the subject matter described herein to people who are familiar with this field. It should be understood that the subject matter described herein may be implemented in various forms without being limited to the described example implementations. The subject matter described herein can be practiced without those specifically defined or described matters or with other or different elements or matters not described. It will be appreciated by those familiar with this field that changes may be made in these example implementations without departing from the subject matter described herein as defined in the appended claims and their equivalents. 

I/W claim:
 1. A system for processing data to generate an output, the system comprising: an automated tagging system that receives data from a plurality of alternate data providers, each of the plurality of data providers having different types of data; wherein the automated tagging system standardizes the different types received from the different data providers by performing filtering, de-duplication, normalization, and classification; wherein the automated tagging system performs updating and feedback by providing an artificial intelligence system that employs neural networks that use back propagation for periodic updates to a training phase; a company financial data unit that provides published information comprising annual reports, press releases, information from the social media of spokespersons or executives, and published pricing information; a modelling system that receives the standardized data of the automated tagging system and the company financial data, the modelling system including one or more handle generators and forecast builders that are applied to the artificial intelligence-based system that employs the neural networks to generate, as an output, a forecast; a revenue prediction unit that receives the output as the forecast, comprising one or more revenue predictions, to generate a final output as a revenue prediction.
 2. The system of claim 1, wherein the different types of data comprise financial transaction information, location information, or consumer behavior information.
 3. The system of claim 1, wherein the input to the modelling system includes proprietary data associated with the merger and acquisition information of the company, and a fiscal quarters calendar of the company.
 4. The system of claim 1, wherein the final output comprises a recommendation to buy, hold or sell, as a transaction, a score, or an execution instruction associated with the transaction without involving the user.
 5. The system of claim 1, wherein a rule-based or other deterministic approach is combined the neural network.
 6. A system for processing data to generate an output, the system comprising: a plurality of inputs, each of the inputs being received from a data source, and each of the inputs being of a different type; a big data system configured to receive each of the plurality inputs, the big data system including, a plurality of adapters corresponding to the plurality of inputs, each of the adapters configured to normalize, deduplicate and classify the data received from the plurality of inputs, to generate outputs, and a modeling system that receives the generated outputs, and provides the generated outputs to a plurality of multi-panel generators, multi-forecast builders and forecaster modules, to generate a revenue prediction; and an access point and provides the revenue prediction in the format of a file, an API, a console or a custom format.
 7. The system of claim 6, wherein data miners and analysts supervise and update the plurality of adapters.
 8. The system of claim 6, wherein the outputs of the plurality of adapters is combined with external data comprising financial reports or other publicly available information associated with historical or present characteristics of an entity.
 9. A computer-implemented method of processing data, the method comprising: a first phase associated with data processing, the first phase comprising, receiving input data from a plurality of sources of different types, normalizing the received data by mapping the received input data from organic formats in which the was received, to a standardized data format that provides consistency across the organic formats by accounting for the differences in the input data from the plurality of sources of different types, and deduplication, to generate normalized data; applying tagging rules to the normalized data, the tagging rules comprising rules that are specific to a credit card or debit card, geo-fencing rules for GPS data, and rules associated with browser history or application usage, to generated tagged data; a second phase associated with development of a panel and calibration, the second phase comprising, performing panelization by establishing a sample of users as a panel based on one or more of input data churn rate, user transaction patterns, census data balancing, or another rules that associates a characteristic of user transaction behavior with a transaction grouping the panels by symbol to associate one or more brands of a company with the tagged data, wherein the grouping is performed in real time to incorporate mergers, acquisitions, spinoffs, bankruptcies, rebranding, listing or delisting associated with the company associated with the symbol; and applying one or more corrections to the grouped panels by applying one or more respective patterns associated with a financial institution to calibrate the grouping, wherein the respective patterns comprise weekend postings of information, posting delays typically associated with a financial institution, and pending but not yet posted transactions, removing anomalies associated with anomalous transactions or anomalous users; and a third phase associated with creating and applying a prediction model, the third phase comprising, generating a prediction model, wherein training data comprises historical data associated with the company including financial parameters of the company, stock price, and historical measurements, generating a forecast by using the generated prediction model and features associated with a current time period, the forecast comprising a prediction of a future stock price.
 10. The computer-implemented method of claim 9, wherein the input data comprises timeseries data from multiple vendors, including credit card transactions, debit card transactions or other electronic purchase transactions.
 11. The computer-implemented method of claim 9, wherein the tagging comprises, for a series of financial transactions, labeling each of the financial transactions by applying the tagging rules to the series of financial transactions, wherein the tagging rules include an inclusive filter or an exclusive filter, and further comprising applying natural language processing based on neural networks. 